Show helpful error message for incorrect API key usage #68
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
✔️ All good! |
shairyar
force-pushed
the
fix-401-error-message
branch
from
f1de5ee to
0a94e50
Compare
unflxw
reviewed
Sep 8, 2025
.changesets/make-it-easy-to-know-if-wrong-api-key-is-being-used.md
Outdated
Show resolved
Hide resolved
- Use is_success() method for proper HTTP status classification - Display human-readable status codes (e.g., '401 Unauthorized')
The changeset aims to be descriptive of the functionality. Co-authored-by: Noemi <[email protected]>
- Simplify log formatting to use status Display trait directly
unflxw
approved these changes
Sep 9, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
When users encounter a 401 Unauthorized error while sending metrics to AppSignal, the current error handling doesn't provide helpful guidance about what went wrong or how to fix it.
Solution
This PR enhances the error logging in the
send_batchfunction to provide a specific, actionable message when encountering a 401 error. It guides users to ensure they're using an app-level API key rather than an organization-level key.